v2.32.0

Compare Source

Minor Changes

• 2b7dd17: Add a gzip option to the template copy layer to control whether copied
  files are gzipped before upload.

  Gzip is enabled by default (matching the previous behavior). Pass
  gzip: false (gzip=False in Python) to upload an uncompressed tar archive
  instead — useful when copying already-compressed files where gzipping adds
  CPU cost without shrinking the payload.

  // JS/TS
  template.copy('model.bin', '/app/', { gzip: false })

  # Python
  template.copy('model.bin', '/app/', gzip=False)

Patch Changes

• bb45f18: Introduce a generic, reusable paginator base class and migrate the sandbox and snapshot list paginators onto it. The base owns the shared cursor-based pagination state (hasNext/has_next, nextToken/next_token, and reading the x-next-token header) while each concrete paginator implements nextItems/next_items to fetch its own page, so future list endpoints can add pagination by subclassing it without reimplementing the bookkeeping. No public API changes.
• f160f08: Keep integration user-agent attribution on ConnectionConfig instead of exposing it through sandbox, template, volume, or per-call API option types.
• c385566: Correct Sandbox.list() documentation across both SDKs: it returns a paginator (SandboxPaginator / AsyncSandboxPaginator), not a list, and by default the server returns sandboxes in both running and paused states. The docstrings now describe the return type accurately and show how to iterate pages via paginator.next_items() / await paginator.nextItems() while paginator.has_next / paginator.hasNext is true. No behavior change.
• bb16968: Template builds: the build-context tar archive is now spooled to a temporary file and streamed from disk during upload instead of being held in memory (JS and Python, sync and async), while keeping the explicit Content-Length required by S3 presigned URLs. Temp-file cleanup is now best-effort, so a cleanup failure after the upload no longer masks a successful upload as an error (nor overwrites the real upload error on failure). The Python SDK now uploads the archive with a 1-hour default timeout (overridable via request_timeout) instead of the 60s general API timeout, matching the JS SDK and preventing large uploads from timing out.

v2.31.0

Compare Source

Minor Changes

• 7e7e951: Add an object form to the sandbox lifecycle.onTimeout (on_timeout in Python)
  that controls the snapshot kind taken when a sandbox auto-pauses on timeout, via
  keepMemory (keep_memory).

  onTimeout now accepts either the existing bare action ('pause' / 'kill') or
  the object form. The object form is a discriminated union on action:
  keepMemory is only accepted alongside action: 'pause' — pairing it with
  action: 'kill' is a compile-time type error (and is rejected at runtime for
  untyped callers). When keepMemory is false, a timeout auto-pause drops the
  in-memory state and persists only the filesystem (a filesystem-only snapshot);
  resuming such a sandbox cold-boots (reboots) it from disk, losing running
  processes and open connections. Defaults to true (full memory snapshot). It
  cannot be combined with auto-resume: auto-resume wakes a paused sandbox on
  inbound traffic by restoring its memory snapshot in place, and a filesystem-only
  snapshot has no memory to restore (resuming cold-boots it), so it must be resumed
  explicitly. The bare string form is unchanged.

  # Python
  sbx = Sandbox.create(
      lifecycle={"on_timeout": {"action": "pause", "keep_memory": False}}
  )

  // JS/TS
  const sbx = await Sandbox.create({
    lifecycle: { onTimeout: { action: 'pause', keepMemory: false } },
  })

• cb5a387: Add a keepMemory (keep_memory in Python) option to pause for
  filesystem-only snapshots.

  When keepMemory is false, pausing drops the in-memory state and captures
  only the filesystem (no memory snapshot); resuming such a snapshot cold-boots
  (reboots) the sandbox from disk, losing running processes and open connections.
  Defaults to true (full memory snapshot), so existing callers are unaffected.

  # Python
  sbx.pause(keep_memory=False)          # filesystem-only snapshot

  // JS/TS
  await sandbox.pause({ keepMemory: false }) // filesystem-only snapshot

Patch Changes

• de0c401: Fix three filesystem watch handle bugs:
  • JS: WatchHandle now awaits async onEvent/onExit callbacks. A rejecting async onEvent is routed to onExit and stops the watch instead of becoming an unhandled promise rejection that can crash Node, and async callbacks get backpressure/ordering — matching CommandHandle.
  • Python (sync): WatchHandle.get_new_events() and stop() now send a request timeout (default 60s, overridable via request_timeout) so a stalled call can't hang the thread forever, and include the authentication header so the polling/stop calls aren't sent unauthenticated on older envd.
  • Python (async): AsyncWatchHandle now invokes on_exit when the stream ends cleanly (with None) and when stop() is called, in addition to on error — matching the JS SDK.